Potential fix for code scanning alert no. 5: Workflow does not contain permissions#212
Merged
Merged
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Novaes
requested review from
aaudzei,
danhellem,
kboom,
nikolapeja6 and
skmanoj
as code owners
danhellem
approved these changes
Jul 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/microsoft/azure-devops-mcp/security/code-scanning/5
To fix the issue, we need to add the
permissionskey to the workflow file. Since the workflow does not require write access to the repository, we can set the permissions tocontents: read. This will limit the access of theGITHUB_TOKENto read-only for repository contents, ensuring the workflow adheres to the principle of least privilege.The
permissionskey should be added at the root level of the workflow file to apply to all jobs (buildandstatic-code-analysis) unless overridden by a specific job.Suggested fixes powered by Copilot Autofix. Review carefully before merging.